Skip to content

chore: un-skip IDE tests#39729

Merged
hetunandu merged 8 commits intoreleasefrom
chore/unskip-ide-tests
Mar 14, 2025
Merged

chore: un-skip IDE tests#39729
hetunandu merged 8 commits intoreleasefrom
chore/unskip-ide-tests

Conversation

@hetunandu
Copy link
Member

@hetunandu hetunandu commented Mar 14, 2025

Description

Mocks a few heavy components that were causing a timeout for IDE tests in EE.

EE PR for tests: https://github.com/appsmithorg/appsmith-ee/pull/6580

Automation

/ok-to-test tags="@tag.IDE"

🔍 Cypress test results

Tip

🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
Workflow run: https://github.com/appsmithorg/appsmith/actions/runs/13855339158
Commit: 205a69f
Cypress dashboard.
Tags: @tag.IDE
Spec:


Fri, 14 Mar 2025 11:40:35 UTC

Communication

Should the DevRel and Marketing teams inform users about this change?

  • Yes
  • No

Summary by CodeRabbit

  • Tests
    • Improved test coverage for our code editor interfaces with enhanced component isolation through mocking.
    • Reactivated previously skipped tests to ensure robust quality validation.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 14, 2025

Walkthrough

The pull request updates two test files by enabling their respective test suites. This is achieved by changing the description from describe.skip to describe, allowing the tests to run. Mocks for the LazyCodeEditor component are introduced in both the JS and Query Render tests to isolate the components under test.

Changes

File(s) Change Summary
app/client/src/pages/.../JSEditor/JSRender.test.tsx, app/client/src/pages/.../QueryEditor/QueryRender.test.tsx Changed test suite descriptions from describe.skip to describe to enable test execution; added mocks for LazyCodeEditor in both test files.

Possibly related PRs

Suggested labels

ok-to-test, IDE Product, Task

Suggested reviewers

  • ApekshaBhosale
  • sagar-qa007

Poem

In test realms, code takes flight,
Mocks now shine in renewed light,
Skips removed, the suites run true,
Each assertion sings something new,
A playful nod to code done right!


📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro (Legacy)

📥 Commits

Reviewing files that changed from the base of the PR and between 1492ed2 and 205a69f.

📒 Files selected for processing (2)
  • app/client/src/pages/AppIDE/layouts/routers/JSEditor/JSRender.test.tsx (1 hunks)
  • app/client/src/pages/AppIDE/layouts/routers/QueryEditor/QueryRender.test.tsx (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (2)
  • app/client/src/pages/AppIDE/layouts/routers/QueryEditor/QueryRender.test.tsx
  • app/client/src/pages/AppIDE/layouts/routers/JSEditor/JSRender.test.tsx
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: client-unit-tests / client-unit-tests
  • GitHub Check: client-lint / client-lint
  • GitHub Check: client-check-cyclic-deps / check-cyclic-dependencies
  • GitHub Check: client-build / client-build
  • GitHub Check: client-prettier / prettier-check

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the skip-changelog Adding this label to a PR prevents it from being listed in the changelog label Mar 14, 2025
@hetunandu hetunandu requested a review from KelvinOm March 14, 2025 06:56
@hetunandu hetunandu added the ok-to-test Required label for CI label Mar 14, 2025
@hetunandu hetunandu marked this pull request as ready for review March 14, 2025 06:57
import { PageFactory } from "test/factories/PageFactory";
import { JSObjectFactory } from "test/factories/Actions/JSObject";

// Mock JSEditorForm component
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hetunandu Thanks for the PR. I see that the execution time of JsRender has decreased by 2 times, but the execution time of QueryReader is still the same. Could you check why this is so?

The timeout is also triggered for each individual it, so you can check which it takes which time with logs, like this

  beforeEach(() => {
    testStartTime = Date.now();
  });

  afterEach(() => {
    const testDuration = Date.now() - testStartTime;
    console.log(`🕒 Test "${expect.getState().currentTestName}" took ${testDuration}ms`);
  });

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not able to remove anything that is not critical. But it is under limits now so we should be good.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can mock not only direct imports, but also what is imported above. Anyway, approved.

I wonder if AI can help mock what's not needed and make tests faster? 🤔

@hetunandu hetunandu removed the ok-to-test Required label for CI label Mar 14, 2025
@hetunandu hetunandu added the ok-to-test Required label for CI label Mar 14, 2025
@hetunandu hetunandu requested a review from KelvinOm March 14, 2025 11:11
@hetunandu hetunandu merged commit 5b3ef55 into release Mar 14, 2025
50 checks passed
@hetunandu hetunandu deleted the chore/unskip-ide-tests branch March 14, 2025 12:08
github-actions bot pushed a commit to Zeral-Zhang/appsmith that referenced this pull request Apr 12, 2025
## Description

Mocks a few heavy components that were causing a timeout for IDE tests
in EE.

EE PR for tests: appsmithorg/appsmith-ee#6580

## Automation

/ok-to-test tags="@tag.IDE"

### 🔍 Cypress test results
<!-- This is an auto-generated comment: Cypress test results  -->
> [!TIP]
> 🟢 🟢 🟢 All cypress tests have passed! 🎉 🎉 🎉
> Workflow run:
<https://github.com/appsmithorg/appsmith/actions/runs/13855339158>
> Commit: 205a69f
> <a
href="https://internal.appsmith.com/app/cypress-dashboard/rundetails-65890b3c81d7400d08fa9ee5?branch=master&workflowId=13855339158&attempt=1"
target="_blank">Cypress dashboard</a>.
> Tags: `@tag.IDE`
> Spec:
> <hr>Fri, 14 Mar 2025 11:40:35 UTC
<!-- end of auto-generated comment: Cypress test results  -->


## Communication
Should the DevRel and Marketing teams inform users about this change?
- [ ] Yes
- [x] No


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Tests**
- Improved test coverage for our code editor interfaces with enhanced
component isolation through mocking.
- Reactivated previously skipped tests to ensure robust quality
validation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ok-to-test Required label for CI skip-changelog Adding this label to a PR prevents it from being listed in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants